home *** CD-ROM | disk | FTP | other *** search
- Path: chronicle.mti.sgi.com!austern
- From: Roman Lechtchinsky <wolfro@cs.tu-berlin.de>
- Newsgroups: comp.std.c++
- Subject: Re: Hiding Overloaded Functions
- Date: 05 Mar 1996 09:42:35 PST
- Organization: Technical University of Berlin
- Approved: austern@isolde.mti.sgi.com
- Message-ID: <313C07C7.7105@cs.tu-berlin.de>
- References: <4h9psh$fnv@news.cs.tu-berlin.de> <xsovikkwkg2.fsf@avs.cs.rpi.edu>
- NNTP-Posting-Host: isolde.mti.sgi.com
- X-Original-Date: Tue, 05 Mar 1996 10:22:15 +0100
- X-Mailer: Mozilla 2.0 (Win95; I)
- X-Auth: PGPMoose V1.1 PGP comp.std.c++
- iQBVAwUBMTx9Iky4NqrwXLNJAQFh7AIAqMRsriXqEEIdCFtAYY5pHR91MhXS/LpX
- k0za8GIDgMIzd4WT++SCMtRdcRWdLEXg9Lo48icVNpO7h3Hc+m06dQ==
- =29vO
- Originator: austern@isolde.mti.sgi.com
-
- David Vandevoorde wrote:
- >
- > >>>>> "RL" == Roman Lechtchinsky <wolfro@cs.tu-berlin.de> writes:
- > [...]
- > RL> In the present standard as well as in the April draft, there
- > RL> exists one rule which I don't like at all. Basically, the concept
- > RL> is that if several overloaded functions are defined in a class A
- > RL> and one of these functions is redefined in a derived class B this
- > RL> function hides all functions inherited from A that have the same
- > RL> name:
- > [...]
- >
- > C++ look-up rules are already quite complicated. If this rule were
- > relaxed the way you suggest, I imagine things would get even worse
- > (I think you would have to define some kind of iteration between
- > name look-up and overload resolution).
- >
-
- I don't see your point. The rules would be no more complicated than they are
- now. The only difference would be that overloaded functions which are hidden
- in derived classes now would be visible. The usual overload resolution could
- be used.
-
- Bye
-
- Roman
- ---
- [ comp.std.c++ is moderated. To submit articles: Try just posting with your
- newsreader. If that fails, use mailto:std-c++@ncar.ucar.edu
- comp.std.c++ FAQ: http://reality.sgi.com/austern/std-c++/faq.html
- Moderation policy: http://reality.sgi.com/austern/std-c++/policy.html
- Comments? mailto:std-c++-request@ncar.ucar.edu
- ]
-